This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
- I appreciate your response, Simon, but the text fully explained everything even if the code were ignored. Specific to your concern:
"As you can see, it caches the current drive and directory, and returns to them on exit, even if the error handler runs. "
The line you mention is it setting the directory back where it started, *away* from the directory it will fail to delete later. All other access to the file placed in that directory is done via full path specifications without changing the current directory again. In fact, the only reason the current directory gets changed at all is to build the directory tree the file will be put in. Don't recall why I did it that way but I surmise it's a hack, er, workaround, for some other flakiness with path-only use and directory creation. The current directory is such a mess in LotusScript that I willingly go far, far out of my way to avoid changing it unless there is no other solution.
- Also:
"But, as mentioned, in the Grand Scheme of flakiness, this ranks next to zero."
I have less than no interest in seeing this fixed. I was simply pointing out that it does in fact happen whether Lotus is able to reproduce it or not, and it has happened for over a decade in numerous different bits of code, none of which are copy/paste from one to the other. I feel it's important that others searching the forum find out it can happen, and work around it, rather than have them believe it's not possible because Lotus hasn't reproduced it. Nothing more.
Thanks for your time...
Feedback response number DGIE85SHPA created by ~Holly Zekhipisonnivu on 05/25/2010